Copyright: ©1993 WUGNET Electronic Docs
Citation: Call WUGNET Electronic Docs! (313) 482-1600


WRK Updates
Updates to the Windows Resource Kit

The Microsoft KnowledgeBase now lists a number of corrections and updates to information in Microsoft's printed Windows Resource Kit.  This file condenses all the corrections and updates we could find, and incorporates a relatively painless update procedure.

How to Update Your WUGNET Online WRK

1.	Make sure this file is in the same directory as your WUGNET Online WRK files!  The WinHelp macros probably won't be able to find your WRK files otherwise.

2.	Find an update topic in this file.  You can search for individual topics using the Search button, or browse them all by clicking on the "Next" button at the top of each topic.

3.	Click the Update WRK button when you find a topic you want to correct.  The update text is placed on the clipboard, and the appropriate WRK file is presented in the Help window.

4.	Click the Notes button at the top of the WRK Help window.

5.	When the Annotate dialog box appears, click the Paste button.  You should see the text box fill up with the topic text automatically copied from this update file.  This box will usually be empty until you click the Paste button; however, some updates affect the same topic.

6.	(Optional) Enter your own notes, or edit the text.

7.	Click on Save to put away the dialog.   You should see a little green paper clip like this one at the beginning of the topic:

8.	Click on the paper clip to see the update text.  To delete the note, click the paper clip, then click the Delete button.

9.	To return to this file, click on the Back button at the top of the WRK Help window.  Click the Next button to move to the next topic update.

How to Find Topics Quickly

If you're doing your search manually, use the Search dialog.  The online WRK includes each topic title as a search keyword.   To find a topic:

1.	Open the appropriate file.

2.	Click on the Search button.

3.	Enter the first word or two of the topic title.  The full topic title is provided in this file.

For example, to find  (9) Specifying Virtual Printer Memory, open WRK file 9, and enter the word

specifying

 in the Search dialog.

How to Print Topics

Click the Print button at the top of your screen.


Pen Documentation Not Online

Error

The online edition of the WRK does not contain the chapter on Windows for Pen Computing.

Correction

WUGNET will provide pen computing information if there is user demand for it.

All information pertaining to this chapter was included with the official release of the Windows 3.1 SDK documentation which included Pen SDK 1.0 information.  Other update information is included in the MS Windows for Pen Computing OEM Adaptation Kit (OAK).

Where the Error is Located

Print  = Pen Computing Appendix

Online = (7) Contents


Virtual Printer Memory

Error

The WRK implies that more details on virtual printer memory can be found in Chapter 4 of the Getting Started with Microsoft Windows guide.  However, no additional information specific to printer virtual memory exists there.

Correction

The section titled "To change a PostScript printer's options" on page 84 of the Getting Started with Microsoft Windows guide does provide information about the Clear Memory Per Page check box.

Other information about virtual memory can be found by choosing the Help button or by pressing F1 while the insertion point is in the Virtual Memory settings dialog box.

Where the Error is Located

Print version = page 334

Online version = (9) Specifying Virtual Printer Memory


IRQ Line in SYSTEM.INI

Error

Flowchart 2.5B states "Leave the IRQ9=Global line in the SYSTEM.INI."

Correction

This line should read: Leave the IRQ9Global=Yes line in the SYSTEM.INI file.

Where the Error is Located

Print = page 23

Online version file and topic = (1) Flowchart 2.5


COMMdrv30=

Error

The WRK incorrectly spells the SYSTEM.INI [386enh] switch for using the Windows 3.1 communications driver, COMdrv30=.

Correction

The correct spelling is COMMdrv30=.

This switch should be set for Yes or True if you are using the COMM.DRV driver that came with Windows 3.0 or using a third-party driver compatible with the Windows 3.0 communication driver, but not with Windows 3.1's driver.

When set to True or Yes, the Virtual COM Driver (VCD) will use its own copy of the serial communications driver's interrupt handler. By default, this line does not exist, which is the same as saying COMMdrv30=False or No.

Where the Error is Located

Print = page 196

Online = (1) [386enh] Section


COM Addresses

Error

The WRK incorrectly reports the I/O addresses and IRQs for COM1, COM2, COM3,  and COM4.

Correction

The correct addresses and IRQs are:

Port	Address	IRQ
COM1	3F8h	IRQ4
COM2	2F8h	IRQ3
COM3	3E8h	IRQ4
COM4	2E8h	IRQ3
Where the Error is Located

Print = pages 343 and 348; also listed incorrectly on page 2 of the COMMQA.WRI file

Online = (4) SYSTEM.INI Modifications for Port Entries in the ROM BIOS Segment


Changing TrueType Names

Error

"Changing Typeface Names for Soft Fonts" states:

If you purchase a TrueType font or other soft font that has the same name as a font you are already using, you should use the Font Installer to change the name of the font.

Correction

TrueType font names cannot be changed using the font installer included in Control Panel.

Where the Error is Located

Print = page 337

Online = (1) Changing Typeface Names for Soft Fonts


COMxFIFO Does Not Properly Understand True and False

Error

The SYSTEM.INI [386enh] setting, COMxFIFO=, is not fully Boolean-aware.  It can be set to either 0 for off or 1 for on, but does not correctly understand True/False, On/Off, or Yes/No. COMxFIFO=1 and COMxFIFO=0 are the usable switches (where x is the  communications port). Microsoft has confirmed this in Windows 3.1.

This switch is used to enable or disable Windows 3.1's support for Windows applications using a COM port with a 16550 Universal Asynchronous Receiver Transmitter (UART). The 16550 has a 16-byte character FIFO buffer, or first-in, first-out buffer.

SYSINI.WRI  incorrectly identifies TRUE/FALSE as functioning with this switch.

The WRK incorrectly identifies On/Off as functioning with this switch.

Correction

COMxFIFO= can be set to either 0 for off or 1 for on.  Do not use True/False, On/Off, or Yes/No.

Where the Error is Located

Print = page 196; also incorrect in SYSINI.WRI

Online = (1) Format of .INI Files


Network Assistant Menu Bar

Error

The menu bar of the for Network Assistant shows menu options having Utilities and Help as choices.

Correction

The menu bar for the Network Assistant utility actually has "File,"  "Window," and "Help" as menu options.

Where the Error is Located

Print = page 440

Online = (6) Network Assistant


Cannot Create Directories by Modifying SETUP.INF File

Error

SETUP/N initiates the Win 3.1 network setup procedures, allowing one to create directories and copy files to user defined networked directories, and the ability to customize these directory settings in SETUP.INF.

The WRK example states that SETUP/N should create the APPDIR directory within the Windows user directory, copying files in the [custom.apps] section.

This is incorrect.

Correction

This directory is never created.  Setup copies these files to the user directory before completing installation.

Where the Error is Located

Print = page 131

Online = (1) Copying Additional Files to a User's Directory


Translation Buffer

Error

The WRK contains inaccurate instructions for placing the 386 enhanced mode translation buffers in upper memory area (UMA).  "Freeing Conventional Memory in 386 Enhanced Mode" states:

Then add an x= switch to the EMM386 line in the CONFIG.SYS to exclude the unused UMB ranges.

In addition, this section also indicates that Windows utilizes these excluded ranges for placement of the translation buffers. This is incorrect; any UMAs excluded by an upper memory block (UMB) provider will also be excluded from use by Windows 3.1.

Correction

The following is a correction to this section:

Windows running in 386 enhanced mode queries any UMB provider (such as EMM386.EXE, QEMM, and 386Max) for information about the UMB area.   Every UMB provider creates a data structure that contains the  following information in 4K granularity (that is, every 4K is marked  as one of the following):

1.	Part of a UMB

Something has been loaded into this address range.

2.	Part of an EMM page frame

The memory is part of a LIM 4.0 page frame.

3.	Part of an EMS page frame

The memory is part of a LIM 3.2 page frame.

4.	Usable

This is the region that is "free." All areas that are marked by an I= parameter in EMM386.EXE but are not actually used will be marked as usable.

5.	Unusable

This is the region that is either RAM, ROM, or specifically excluded (for example, the X= parameter in EMM386.EXE).

6.	Unknown

All addresses that are not scanned will be marked as Unknown. This region will be scanned by Windows as it normally would.

Under Windows 3.0, only #1 (part of a UMB) and #3 (part of an EMS page frame) are looked at.  Thus, address ranges that need to be excluded on the command line for the UMB provider should also be excluded in the [386Enh] section of the SYSTEM.INI with an EMMExclude statement.

Under Microsoft Windows 3.1, the whole structure is looked at, and assumed to be valid.  As a result, the following entries in the [386Enh] section of the SYSTEM.INI are ignored, except where they do not conflict with the structure created by the UMB provider:

EMMINCLUDE
EMMEXCLUDE
RESERVEDHIGHAREA
USEABLEHIGHAREA
IGNOREINSTALLEDEMM
NOEMMDRIVER
EMMPAGEFRAME

For example, if EMM386.EXE is installed with the line

DEVICE=C:\Windows\EMM386.EXE NOEMS

then the line

EMMInclude=B000-B7FF

would be used by Win 3.1 because the B000 region is not scanned by EMM386.EXE. However, the line

EMMExclude=D800-DFFF

will be ignored because this region is scanned by EMM386.EXE.

Where the Error is Located

Print = page 269

Online = (2) Freeing Conventional Memory in 386 Enhanced Mode


MONOUMB2.386 File Size Error

Error

The expanded size listed for MONOUMB2.386 in the LAYOUTS.WRI file included in the Windows Resource Kit (WRK) for Windows 3.1 is listed as 46161 bytes.

Correction

The actual size of the expanded MONOUMB2.386 file is 4745 bytes.

Where the Error is Located

LAYOUTS.WRI


TTIfCollisions=

Error

The WRK  incorrectly documents the TTIfCollisions= entry of the [TRUETYPE] section of the WIN.INI file.  The statement implies that if you set this value to 0, Windows will use the TrueType version.

This is incorrect.

Correction

The correct statement should be:

If you set this value to 1, Windows will use the TrueType version.

This entry actually specifies whether to use TrueType fonts in place of other fonts if both types of fonts are installed on the system and have  the same font name.

Where the Error is Located

Print = page 176

Online = (1) [TrueType] Section


Making a Boot Disk

Error

The WRK gives inaccurate syntax for creating a bootable floppy disk with the FORMAT command.

Step 3 of the section titled "To create  a 'clean boot' disk for troubleshooting" incorrectly states:

Make a boot disk. To do this, place a disk in drive A, type the following command at the command prompt: FORMAT A:.

This syntax does not create a boot disk.

Correction

The correct syntax is: FORMAT A: /S .  The /S switch causes the MS-DOS FORMAT command to copy the MS-DOS operating system files to the formatted disk.

Where the Error is Located

Print = page 398

Online = (6) Creating a "Clean Boot" for Troubleshooting


Creating the FINSTALL.DIR File

Error

The WRK incorrectly documents step 2 as:

In the Font Installer dialog box, hold down the Ctrl and Shift keys and click the Exit button.

Correction

The correct procedure should be:

 	In the Font Installer dialog box, hold down the Ctrl and Shift keys and choose the Add Fonts button.

Where the Error is Located

Print = page 327

Online = (4) Recovering Soft Fonts


Removing Unused Fonts

Error

The WRK provides the following instruction for removing unused fonts:

3.	Make sure the Delete Font File from Disk option is checked, and choose Remove.

4.	When the dialog box prompt appears, choose Yes to remove the file.

This is incorrect.

Correction

The correct instructions are:

3.	Choose Remove. The Remove Font dialog box appears. Make sure the Delete Font From Disk check box is selected.

4.	Choose Yes to remove the file.

Where the Error is Located

Print = page 501

(not included in the online edition)


SMARTDrive Cacheing and Stacker

Error

The fifth flowchart in the WRK states:

The SMARTDrive command line can be edited to allow caching of "stacked" volumes by adding a +<drive> (where <drive> is a "stacked" volume). If caching...

 The +<drive> parameter is incorrect.

Correction

The correct command line syntax to turn on the SMARTDrive disk cache is as follows:

C:\WINDOWS\SMARTDRV.EXE <drive>+ .

SMARTDrive will automatically detect the existence of Stacker and cache the underlying Stacker drive.  SMARTDrive should not be used to cache a Stacker volume.

Typing SMARTDRV /? at the MS-DOS prompt lists the command line parameters for SMARTDrive, with their meaning.

Where the Error is Located

Print = Flowchart 1.8

Online = (1) Chart 1.8


IRQ 2 Setting

Error

The WRK states:

Do not use INT 2, INT 9, or above and do not use a base I/O port address below 300 for your LAN card (such as ARCNET or Token Ring) unless you use VPICDA.386, which you can obtain from either Microsoft or Novell.

Correction

Windows 3.1 does not require VPICDA.386 to work with IRQ 2 in the Novell network environment.

Also, the words INT 2 and INT 9 as stated above should be IRQ 2 and IRQ 9.

Where the Error is Located

Print = page 391

Online = (5) Novell NetWare


Sound Blaster Driver

Error

The WRK incorrectly states the association of Sound Blaster drivers and versions as follows:

SNDBLST.DRV=SoundBlaster 1.5 DSP driver

SNDBLST2.DRV=SoundBlaster 2.0 DSP driver.

Correction

The correct associations are:

SNDBLST.DRV=SoundBlaster 1.0 DSP driver

SNDBLST2.DRV=SoundBlaster 1.5 DSP driver

Owners of the Sound Blaster Pro card (which have DSP versions 3.x) can use SNDBLST2.DRV, but Windows may display a warning message when setting the port and IRQ, indicating that new drivers are needed from the manufacturer.

Drivers can be acquired through Creative Labs technical support, (408) 428-6622, or the Creative Labs BBS, (408) 428-6660, (408)428-6662, or (408) 428-6664.

Where the Error is Located

Print = page 143

Online = (1) Multimedia Driver Files


32-Bit Disk Access

Error

The item in the subheading titled "To ensure optimal speed performance" states:

Use 32-bit disk access to speed up the access time to hard disk. For a technical discussion of this feature, see "FastDisk: An Introduction to 32-Bit Disk Access" in Appendix D.

Correction

Chapter 6 of WRK is dedicated to Windows performance tips. 32-bit  disk access is a speed enhancement feature in Windows 3.1.

Where the Error is Located

Print = page 262

Online = (2) Creating Swap Files for Virtual Memory


Order= Line in PROGMAN.INI

Error

The Order= line of the PROGMAN.INI file is incorrectly placed under the [Groups] section.

Correction

The Order= line should be under the  [Settings] section as follows:

[Settings]

order=1 2 3 4 5

Where the Error is Located

Print = page 220

Online = (1) [groups]


Stacker and Permanent Swap Files

Error

The "Creating Swap Files for Virtual Memory" section incorrectly states the following:

You cannot create a permanent swap file if Stacker is running on your system.

Correction

You cannot create permanent swap file on a compressed (Stacked) drive, because an uncompressed contiguous space is required for a permanent swap file. Stacker is manufactured by Stac Electronics,

Where the Error is Located

Print = page 244

Online = (2) Creating Swap Files for Virtual Memory


TESTPS.TXT Directory

Error

Flowchart 4.1, "Cannot Print on Stand-Alone PC" suggests copying the TESTPS.TXT file from the WINDOWS directory to the PostScript printer if you have a PostScript printer.

Correction

The TESTPS.TXT file is installed by Windows in the WINDOWS\SYSTEM subdirectory, not the WINDOWS directory.

Where the Error is Located

Print = Flowchart 4.1

Online = (1) Chart 4.1


Wingdings Font

Error

The WRK does not list Wingdings as a character set that is  installed with Windows 3.1.

Correction

A line should be added that reads:

Wingdings***  TrueType, proportional, scaleable

***Wingdings character set, rather than ANSI character set

Where the Error is Located

Print = page 317

Online = (4) How Windows Matches Fonts


T3100/20 Laptop BIOS

Error

The WRK incorrectly states that BIOS version 4.2 or later is necessary for the T3100/20 laptop computer to run Windows.

Correction

The T3100/20 will work with Windows 3.0 with a BIOS of 2.01, provided  CGA is selected as the display.

Where the Error is Located

Print = page 12

Online = (1) Chart 1.4


Phoenix ROM BIOS Updates

Error

Chart 1.4 states :

According to Phoenix, any BIOS dated earlier than 1988 should be upgraded. There are several OEM versions of Phoenix BIOS that cause problems. Contact the computer manufacturer for more information.

Correction

The information above should state:

 ...any BIOS dated 1988 and earlier should be upgraded.

Where the Error is Located

Print = page 12

Online = (1) Chart 1.4


LANMAN10.386

Error

The flowchart incorrectly uses the term LANMAN10.DOS where LANMAN10.386 is intended.

Correction

Substitute LANMAN10.386.

Where the Error is Located

Print = page 21

Online = (1) Chart 1.7


MINOUTLINEPPEM PostScript Setting

Error

Section 4.5, "Controlling True Type Font Downloading on PostScript" of the PRINTERS.WRI file incorrectly spells the WIN.INI PostScript setting as

minoutlineppem=<number>

where <number> refers to points per em space (an em space is a unit of  measurement where the width of the space is about as wide as it is tall). Using the incorrect spelling results in Windows using the default value of 101 points per em space.

Correction

If you change the minoutlineppem setting, you must exit and restart Windows for the changes to take effect.

Where the Error is Located

PRINTERS.WRI file


PFM Editor Kit Availability

Error

The WRK incorrectly states that the PFM Editor Kit is available from Microsoft Product Support Services.

Correction

The PFM Editor Kit is only included with the Microsoft Windows Device Development Kit (DDK). The DDK comes the Windows Printers and Fonts Kit, which includes information on the Printer Font and Cartridge Metrics (PFM and PCM) file formats, the new PFM Editor, and technical notes on PCL/HP LaserJet and PostScript printer drivers.

Where the Error is Located

Print = page 324

Online = (4) Font Cartridges


SETUP.SHH File Requests Directory During Setup

Error

The WRK states that if the [windir] section of the SETUP.SHH (the settings template file) is left blank, Windows Setup prompts you for a directory. This information is incorrect.

Correction

SETUP.SHH is used to create a custom system settings file with the SETUP /H option to create a custom SETUP.INF. If the directory is not specified in the [windir] section, the dialog box never appears, and Windows installs to the default directory

To correct this:

1.	Add the line "C:\* " (without quotation marks) to the [windir] section of SETUP.SHH:

[windir]

C:\*

where C:\* is an invalid directory, and this entry forces Setup to prompt you for a valid directory. Setup displays a red warning box that states that an error has occurred and asks you to press ENTER to continue or press F3 to exit.

2.	Press ENTER. The next screen prompts you for the correct directory.

3.	Type the name of the directory where you want to install the Windows user files.

4.	Press ENTER.

Where the Error is Located

Print = page 78

Online = (1) [windir]


Loading SMARTDRV.EXE

Error

The WRK incorrectly states that SMARTDRV.EXE must be loaded into 640K conventional memory and cannot be loaded high. SMARTDRV.EXE in the AUTOEXEC.BAT file will load itself into upper memory blocks (UMBs) if they are available and are managed by MS-DOS 5.0 with the command DOS=UMB. If a third-party memory manager is used (such as QEMM or 386MAX), consult their documentation.

Correction

SMARTDRV.EXE installed in the CONFIG.SYS file for double buffering must not be loaded high.

Also, the WRK states that HIMEM.SYS and EMM386.EXE must be loaded in conventional memory; this is partially correct. A  DEVICEHIGH command for these drivers will have no effect. Once they are loaded, however, these drivers do use memory beyond the 640K conventional memory.

Where the Error is Located

Print = page 414

Online = (6) Troubleshooting MS-DOS Configuration Problems


iNegCurr= Value in WIN.INI [intl] Section

Error

The WRK lists an incorrect value for the iNegCurr= entry in the [intl] section of the WIN.INI file. The iNegCurr parameter indicates the format to use for negative values for currency. The values for both "($1)" and "$ 1-" are stated as having the iNegCurr value of 0.

Correction

The correct value for both "($1)" and "$ 1-" should be 10.

Valid entries for the iNegCurr= entry are:

Value	Format
0	($1)
1	-$1
2	$-1
3	$1-
4	(1$)
5	-1$
6	1-$
7	1$-
8	-1 $
9	-$ 1
10	$ 1-
For example, the entry iNegCurr=5 would cause a negative currency value to be displayed in the format "-1$".

Where the Error is Located

Print = page 172

Online = (1) [intl] Section


HIMEM.SYS Machine-Type Chart

Error

The chart displayed refers to the HIMEM.SYS driver version for Windows 3.0, not Windows 3.1.

Correction

The proper switches for Windows 3.1 HIMEM.SYS are documented on page 545 of the Microsoft Windows User's Guide for version 3.1.

Where the Error is Located

Print = page 419

Online = (6) Troubleshooting Windows Running in Standard Mode


Novell Server Log On, Log Off, Attach, Detach

Error

The WRK contains documentation errors concerning the logging on, off, attaching and detaching to Novell Servers. It states:

Do not try to log on, log out, attach, or detach a Novell server  from the MS-DOS Prompt within Windows. You must perform these operations before starting Windows.

Correction

It should state:

Do not try to log on, log out, attach, or detach a Novell server from the MS-DOS Prompt within Windows. You must log on or log out before starting Windows. You can attach and detach from Novell servers through File Manager before starting Windows.

Where the Error is Located

Print = page 388

Online = (5) Novell NetWare


Win 3.1 Support for VCPI

Error

Incorrectly states that Windows 3.1 supports VCPI in both standard mode and 386 enhanced mode. Windows 3.1 is a Virtual Control Program Interface (VCPI) client in standard mode (using DOSX.EXE). Windows 3.1 in 386 enhanced mode is a DOS Protected Mode Interface (DPMI) server (using WIN386.EXE); it does not support VCPI. While it is possible to run specific VCPI applications in standard mode, it is impossible to run VCPI applications in enhanced mode.

Correction

MS-DOS 5.0's HIMEM.SYS version 2.77 or later has the /INT15=xxxx switch for running older VCPI mode apps. Windows standard and enhanced mode do not use INT15 or MS-DOS apps run from Windows. Some MS-DOS applications that can switch from INT15 VCPI to XMS VCPI when INT15 is not available are able to run from Windows' standard mode.

XMS can be used for data storage, DPMI calls, and VCPI calls. Windows standard mode uses XMS as data storage and VCPI (DOSX.EXE is a VCPI client). Windows in 386 enhanced mode can use XMS for data storage and  DPMI (WIN386.EXE is a DPMI server).

Extended Memory Use	MS-DOS	Standard Mode Windows	386 Enhanced Mode Windows
INT15 data	Yes, with /INT15=	No	No
INT15 VCPI	Yes, with /INT15=	No	No
XMS data	Yes	Yes	Yes
XMS VCPI	Yes	Yes	No
XMS DPMI	Yes	N/A	Yes
Standard mode can run some VCPI applications because when the MS-DOS- based application is run, Windows (except for DOSX.EXE) is swapped to disk or XMS data. This leaves the MS-DOS application free to use any XMS calls or usage it needs. Windows in standard mode understands how to allocate memory from a VCPI provider (server), or a DPMI provider.

Where the Error is Located

Print = page 248

Online = (2) DPMI and VCPI Specifications


CONTROL.INI [MMCPL| Section Can Make Control Panel Disappear
[MMCPL] Makes Control Panel Disappear

Error

The X= entry in the CONTROL.INI file is the horizontal window coordinate and the Y= entry is the vertical window coordinate. When these numbers are negative, the Control Panel starting location will  be off the edge of the screen.

If the X= and/or Y= entry is a low enough negative number, Control Panel may appear to not start.

However, if you open the Task List (press Ctrl+Esc or double-click the Desktop), it will show the Control Panel  as a running application. If Control Panel is selected and you choose  the Switch To button, the application you switch to will be the one  that was active before opening the Task List. This happens because the Control Panel is running outside of the screen area.

The WRK briefly describes the [MMCPL] section of the CONTROL.INI file as the section that Specifies values related to the multimedia items in Control Panel.  However, it makes no mention of the NumApps=, X=, Y=, W=, and H= entries that do not pertain to the multimedia items in Control Panel.

Correction

Use a text editor (for example, Notepad), to open the CONTROL.INI file and change any negative numbers to positive numbers.

Where the Error is Located

Print = page 222

Online = (1) CONTROL.INI: Control Panel Initialization File


what
Sorry!

This is just a demo paper clip.  The real thing appears only at the top of a topic.


End

No more updates!


Oops
For this topic only...

WinHelp won't be able to paste in all the text contained in this update topic.

Please use the Edit menu and select only the Correction text.

When you're ready, click on the Update WRK button to jump to the proper topic.